From: Joey Hess Date: Wed, 1 Oct 2025 16:03:54 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20251029-1+rpi1~1^2~3^2~36 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=dce65adeca39643143569a9b7c7bb637d7173131;p=git-annex.git comment --- diff --git a/doc/todo/import_tree_from_rsync_special_remote/comment_7_9716fc56ccfb622c964a64b37c1c5fdc._comment b/doc/todo/import_tree_from_rsync_special_remote/comment_7_9716fc56ccfb622c964a64b37c1c5fdc._comment new file mode 100644 index 0000000000..1036bbd920 --- /dev/null +++ b/doc/todo/import_tree_from_rsync_special_remote/comment_7_9716fc56ccfb622c964a64b37c1c5fdc._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2025-10-01T15:35:53Z" + content=""" +I wonder how sshfs manages stable inodes that differ from the actual ones? +But if it's really reliably stable, it would be ok to use it with the +directory special remote. + +Extending the external special remote interface to support +[import](https://git-annex.branchable.com/design/external_special_remote_protocol/export_and_import_appendix/#index1h2) +would let you roll your own special remote, that could use ssh with +rsync or whatever. + +The current design for that tries to support both import and export, but +noone has yet stepped up to the plate to try to implement a special remote +that supports both safely. So I am leaning toward thinking that it would be +a good idea to make the external special remote interface support *only* +import (or export) for a given external special remote, but not both. + +Then would become pretty easy to make your own special remote that +implements import only. Using whatever ssh commands make sense for the +server. +"""]] diff --git a/doc/todo/importtree_only_remotes.mdwn b/doc/todo/importtree_only_remotes.mdwn index 8f140c9450..2f9174b670 100644 --- a/doc/todo/importtree_only_remotes.mdwn +++ b/doc/todo/importtree_only_remotes.mdwn @@ -32,7 +32,9 @@ the wrong content. (So the remote should have retrievalSecurityPolicy = RetrievalVerifiableKeysSecure to make downloads be verified well enough.) I said this would not use a ContentIdentifier, but it seems it needs some -simple form of ContentIdentifier, which could be just an mtime. +simple form of ContentIdentifier, which could be just an mtime +(but mtime or mtime+size is not able to detect swaps of 2 files that share +both; using inode or something like that is better). Without any ContentIdentifier, it seems that each time `git annex import --from remote` is run, it would need to re-download all files from the remote, because it would have no way of knowing